The Elements of Scrum by Chris Sims & Hillary Louise Johnson

Author:Chris Sims & Hillary Louise Johnson [Sims, Chris & Johnson, Hillary Louise]
Language: eng
Format: epub
Publisher: Dymaxicon
Published: 2011-02-15T05:00:00+00:00

Task count. Some teams have simplified matters even further, and merely count the number of remaining tasks. Then they track this count over the course of the sprint. While it’s true that some tasks are bigger than others, many teams seem to get a useful amount of visibility and predictability this way. This approach has the added benefit of being extremely simple; it has the disadvantage of not inherently alerting the team when a task is too large.

Which approach is best? That’s a decision for the team. Remember, the goal is to get enough early warning when the team is off schedule to be able to do something about it.

The list of all the committed stories, with their associated tasks, and any additional tasks (such as improvement tasks that came out of the team’s retrospective) are collectively referred to as the sprint backlog. This is the list of things the team will get done and deliver by the end of the sprint.

We’ve talked a lot about the team committing to deliver the stories in the sprint backlog. The product owner, on behalf of the business, is also making some commitments. The product owner agrees not to ask for additional stories during the sprint, unless the team specifically asks for more. The product owner also commits to being available to answer questions about the stories, negotiate their scope, and provide product guidance until the stories are acceptable and can be considered done.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.